home *** CD-ROM | disk | FTP | other *** search
- Path: ida.his.se!usenet
- From: a95hanne@ida.his.se (Hannu Nevalainen)
- Newsgroups: comp.os.linux.advocacy,comp.sys.mac.advocacy,comp.os.os2.advocacy,comp.sys.amiga.advocacy
- Subject: Re: Macs Rule.
- Date: 26 Jan 1996 01:05:49 GMT
- Organization: University of Skoevde
- Message-ID: <5501.6599T57T1005@ida.his.se>
- References: <4e695l$t3b@nuke.csu.net>
- NNTP-Posting-Host: oden.ida.his.se
- X-Newsreader: THOR 2.22 (Amiga;TCP/IP) *UNREGISTERED*
-
-
- ** On 24-Jan-96 22:43:17 Gregory L Hansen
- ** <ghansen@isc.sjsu.edu>
- ** wrote to Alla
- ** about "Re: Macs Rule."
- ** in "comp.sys.amiga.advocacy"...
-
- >>> <snippped>
- >> Wait(), -- Wait for any event (may be multiple)
- >> WaitIO(), -- Wait for an asynchronous IO-event to finish.
- >> WaitPort() -- Wait for any "message" to arrive at a "MsgPort"
- >>
- >> for Amigas.
-
- > Something very much like that. Except WaitNextEvent() returns an event
- > record that tells you what kind of event it was, and an event message
- > that gives you other relevant information. And "true" or "false"
- > depending on whether an event occurred, but that's sort of redundant when
- > the event record returns nil for no event.
-
- That would be combining the Amiga funcs WaitPort() and GetMsg().
-
- > ... . In a single
- > tasking system the OS would simply return the event information. In a
- > multitasking system the OS would also decide if it's time to switch to
- > another process.
-
- That is what happens in AmigaOS.
-
- > know if you can do the same with a background task. The menubar clock
- > stops when I press the mouse button, but I'm pretty sure it kept going
- > the last time I tried it. I don't know what's up with that.
-
- When you press the menu-button in AmigaOS (Right Mouse Button) all output on
- that Screen is(/are?) delayed. That could be thought of as a "lazy mans hack",
- but in real life - it really doesn't make much diffrence. You can actually stop
- scrolling text (e.g. from "type file"), so that you can read it, by holding a
- mouse button.
-
- If you don't know what a "Sceen" is:
- Windoze, and as I reccon, MacOS has *one* "screen" - a "table" on which you
- can make things happen. In AmigaOS there can be as many of those as (CHIP)
- memory permits. These screens can be shuffled around almost as a bunch of
- real-life clipboards. There is one restriction; they can't share the
- monitor-display *width*; i.e. only one at a time _horisontally_.
-
- [ CHIP-memory; first MB, or 2MB on the latest machines, that is
- accessible by the special purpouse chips present in an Amiga]
-
-
- >> On the Amiga - most software (including drivers, handlers, ...) does run as
- >> separate processes, e.g.
- >> ...
- >> all can be handled in an asynchronous manner (among other things).
-
- > handle the print job and let you continue your work. But it's still
- > cooperative multitasking. So you can't get much done when you're
- > formatting a floppy.
-
- One, two, three or four floppies beeing formatted doen't make much diffrence
- for AmigaOS. No noticeable hindrance.
-
- I've investigated disk formatting times; just for fun: ;-)
-
- == Amiga DiskFormatting : time m:ss = per disk= (REAL MEASURED TIMIMG)
- »»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»» (Using an Amiga 500 )
- Single disk, one drive : 100s =1:40, =1:40/disk
- Two disks, two drives : 170s =2:50, =1:25/disk
- Three disks, three drives: 252s =4:12, =1:24/disk
-
- That is: formatting 100 disks using ONE drive will take 100*100 seconds:
- 2h 46m 40s excluding swapping the disks.
- formatting 100 disks using TWO drives will take 170*50 seconds:
- 2h 21m 40s excluding disk swaps.
- formatting 99 disks uings three drives will take 252*3 seconds:
- 2h 18m 36s excluding disk swaps.
-
- *AND* during that time you could write... compile... and link a program, print
- couple hundred pages of text, render 24 bit images... generate some fractals...
- depending on the "power" in your Amiga. (I'm running an 68030+68882 @ 50MHz).
-
- Simply said: That's multitasking.
-
- >> < ... AmigaOS bragging... ;-) >
- > Now kernels are something every says will come with Copeland, due out in
- > about a year. And a reentrant toolbox, so they say, will come out with
- > Gershwin, due out a year after Copeland. And it seems like Gershwin will
- > fulfill the wish list of full preemptive mulitasking, multithreading,
- > protected memory, good virtual memory, blahblahblah on a level the UNIX
- > or WindowsNT. Yes, as a Mac enthusiast, I have to admit that although
- > Copeland will deliver most of it in a year, we'll still have to wait two
- > years for "the works".
-
- I've seen text docs on the net stating that PowerPC-based Amigas will be
- available within the first quarter (three months) _THIS_ _YEAR_. The fulfillment
- of that prediction (made by Amiga Technologies, I believe) will show us how
- trustworthy they (A.T.) are.
- Nothing said about pricing and contents of that machine.
- [ I think I read about a PPC 604 though ]
-
-
- >>NOTE: I do not claim that all of my writing is _100_% correct... ;-)
- Still applies.
-
- >>/Hannu E. K. Nevalainen, Amiga user since '85.
-
- > Greg Hansen, Mac user since '95. September.
- > (Actually, I've *used* them before in school labs. That's why I knew I
- > preferred Macs over Windows. But I've only *owned* one since Sept.)
-
- I bought my first Amiga in 1988 (I think), my brother has one, my sister had
- one, another brother is still running one... (I made them buy it)
-
- As I know a man who was (and still is) a Amiga-retailer, I had access to one of
- the first Amiga 1000's back in 1985. I used to demonstrate it for the customers.
- (It had 512K memory, one 880K drive, no HD)
-
- /Hannu E. K. Nevalainen, Amiga user since '85.
- --
- >> Have a look at *http://www.amiga.de/* to inform yourself...
- <tsb> A "Tag" follows... Name: /NoTag_2/á
-
- Tag? Ehh... What's that?
-
- <tsb> I began writing this message 25-Jan-96 23:57:29, local time.
-
-